Conversation
|
Update on the arm build issue(s): I tried cross-compiling and "native-compiling" for aarch64. After adding Here are my test results: cross-compile on x86_64: Variant 1: ./xbps-src -a aarch64 pkg nomacs error message after almost finishing building: Variant 2: ./xbps-src -A aarch64 pkg nomacs error message immediately after executing the command:
compiling on aarch64 (rpi4): ./xbps-src pkg nomacs error message at the end of the config test:
This one is especially annoying, because the allegedly missing file is in |
1 participant
Testing the changes
Local build testing
Note: The package builds, installs and runs fine with the template as proposed, but the readme states the following:
"Build options and their dependencies
This is the list of configurable packages and what they provide in nomacs. To ensure a feature is included/excluded set the cmake option for that feature. By default, all features are enabled if the dependencies are found when running cmake**.
The following Qt components are necessary:
Core, Concurrent, Network, PrintSupport, SVG, Widgets, Core5Compat."Of these dependencies only
qt6-svg-develwas already present from previous versions. I addedqt6-qt5compat-develbecause the build would otherwise fail.The packages
qt6-core qt6-concurrent qt6-network qt6-printsupport qt6-widgetsaren't necessary for building without error messages.But as they are explicitly mentioned, I wonder if I should still add them. I wouldn't know, though, where to add them - to
makedepends,hostmakedependsor evendepends?Another question would be the added
-DENABLE_QUAZIP=1.I did a build test with the previous version and during checks it said that quazip was enabled. Without any changes to the template in that regard for the new version, it would say that quazip was not included. So, I added the argument. I also did a test install with both options. With the added argument, the install would also install quazip-qt6, without the argument, it would not. I'm not sure if nomacs would be able to use the qt5 version of quazip that the previous version depended on. The qt5compat dependency might allow for that - or not, I don't know. So, the question would be if the added argument is needed or if it would be incompatible with the pre-existing argument
-DUSE_SYSTEM_QUAZIP=1.